Skip to main content

Pulse for Elastic Cloud

Pulse Agent Configuration​

If you haven't done so yet, follow the instructions under the Pulse Agent integration section for installation and basic configuration instructions.

The clusters section of the configuration file should point to the cloud ID of the Elastic Cloud cluster - you can find it in the Manage screen for the cluster in the Elastic Cloud console. Specifying username and password for protected clusters is supported, see below for best practices for creating that user.

clusters:
  - type: elastic-cloud
    cloudId: XXXXXX:YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
    username: pulse-monitoring-collector
    password: pwd

Setting Up A Dedicated Monitoring User​

It is highly recommended to provide the agent with credentials for a dedicated user with just the required permissions. This is possible to do via API (see example below or the official documentation) or using Kibana. The built-in role to use is called remote_monitoring_collector. You'll also need to add a new role to support monitoring of snapshots.

PUT _security/role/pulse-additional-priviliges
{
    "cluster" : [
      "monitor_snapshot"
    ],
    "applications": [
   {
     "application": "kibana-.kibana",
     "privileges": [
       "feature_stackAlerts.read"
     ],
     "resources": [
       "*"
     ]
   }
 ]
}
POST /_security/user/pulse-monitoring-collector
{
  "password" : "L0ng-r4nd0m-p@ssw0rd",
  "roles" : [ "remote_monitoring_collector","pulse-additional-priviliges"],
  "full_name" : "Cluster metrics collector for Pulse",
  "email" : "support@bigdataboutique.com"
}